According to Google PlayStore, apps that contain or feature user-generated content (UGC), which include platforms like Twitter, Facebook, and Threads, must implement robust, effective, and ongoing UGC moderation. Google describes UGC as the content which is contributed to an app by users and which is accessible by “at least a subset of the app's users”.
You could write a mod_client in Prosody, which would make it into a client on its own. 😃I think this exists, sort of
so reading through XEP-0402, if i want to make a p2p client with that i basically have to "fake" a server in my library don't I?I think it is 🙂 whether you call it "fake" or not you need a "server"
I think the LAN p2p is still useful, but only on a lan of course. It's fun at conferences for exampleBut why bother when it's even easier to just run a server
singpolyma, not any more, because no one else is using it any more, because clients dropped support.Clients drop support for lots of things, can always add it back
is https://xmpp.org/extensions/xep-0246.html advisable for implementation?Hmm well you need to come up with a good way to authenticate the connections, if you are talking client-to-client they don't have ways to generate certs each other can trust yet
well i dont want to write a server and strap it to my library though 😛you could masquerade as a server and just not send client stanzas ever lol
Somebody who is, or something that is, at a level or of a value equal (to that of something else).ok strictly speaking, sure
i am asking because the serverless messaging is historical obviously0174 is finalised so i wouldnt say historical, just lack of support now because who the hell messes with mdns for messaging
there is https://xmpp.org/extensions/xep-0247.html Rekt: Note: It is STRONGLY RECOMMENDED to encrypt all end-to-end XML streams as described in Jingle-XTLS (currently located at http://xmpp.org/extensions/inbox/jingle-xtls.html). Those security flows are NOT described here.
i could see it useful in an organisational setting but typically corporations will be hosting a server anyway, so most use cases even for that are kinda mehAnd few organizations have everyone in the same building on the same network
Hmm server discovery via dht you say? Intriguing...Now I can't stop thinking about this
There is nothing in any of these standards that would prevent me from including a 1 gigabit MPEG movie of me playing with my cat as one of the RDN components of the DN in my certificate. -- Bob Jueneman on IETF-PKIX
Hmm server discovery via dht you say? Intriguing... Now I can't stop thinking about this What's the advantage over DNS?
Sharing public key hashes over OMEMO or similar would workspecifically this https://xmpp.org/extensions/xep-0250.html
Now I can't stop thinking about this What's the advantage over DNS? Having thought about it for 2 minutes, it could be a solution for hosting XMPP servers securely without domain names or DNS without resorting to Tor
What's the advantage over DNS? Having thought about it for 2 minutes, it could be a solution for hosting XMPP servers securely without domain names or DNS without resorting to Tor Yes. Records will have similar advantage as a .torrent. It would be pretty cool
Sharing public key hashes over OMEMO or similar would work specifically this https://xmpp.org/extensions/xep-0250.html
but with omemo i'm experiencing some terrible omemo bug with Profanity atm... to the point i'm for now only using Conversation so not too sure on this one.
lets take a step back, we're talking about dht to essentially share ip addresses, right? why not just compare it to bittorrent at this rateBasically yes, but they'd need signed etc
pray tell how "onion names" are useful in any way hereYou want to set up a server but don't own a domain name
you have my pubkey, how are you gonna connect to me, lolGetting your signed connection details from a dht